home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20030409-20031118
/
000256_icurmtdude@yahoo.com_Thu Sep 4 10:55:04 EDT 2003.msg
< prev
next >
Wrap
Text File
|
2020-01-01
|
2KB
|
68 lines
Article: 14496 of comp.protocols.kermit.misc
Path: newsmaster.cc.columbia.edu!panix!newsfeed.media.kyoto-u.ac.jp!newsfeed.icl.net!newsfeed.fjserv.net!diablo.theplanet.net!news.maxwell.syr.edu!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: icurmtdude@yahoo.com (icurmt)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: missing bytes...
Date: 4 Sep 2003 07:40:06 -0700
Organization: http://groups.google.com/
Lines: 49
Message-ID: <cf6cc183.0309040640.11263a4b@posting.google.com>
References: <cf6cc183.0309031713.73a00933@posting.google.com>
NNTP-Posting-Host: 24.97.119.28
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1062686407 18505 127.0.0.1 (4 Sep 2003 14:40:07 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 4 Sep 2003 14:40:07 GMT
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14496
Looks like the INPUT (\v(input)) operations discard and ignore NUL
characters that arrive from the communication device. Is there any way
that can be turned on or use some other operation instead of INPUT.
Ray
icurmtdude@yahoo.com (icurmt) wrote in message news:<cf6cc183.0309031713.73a00933@posting.google.com>...
> Hi everyone,
>
> After no luck with this issue, I thought of posting it here.. Heres
> what I am trying to do..
>
> I am sending out commands out of a file through serial port to my
> application which returns me the response accordingly in return..
>
> <code snippet...>
> ..
> ...
> transmit /binary /noecho /nowait <commandsfile>
> input 1 -1
> .output := \fhexify(\v(input))
> echo \m(output)
> ...
> fopen /write \%c <outputfile>
> ..
> fwrite /line \%c \m(output)
> ..
> fclose \%c
>
> </end>
>
> The script works fine. The response as under is outputted to the
> 'outputfile'. Now when I echo the response I get
>
> 16 06 14 34 47 12 01 87
> instead of
> 16 06 14 34 47 12 00 01 87 00 00 00
>
> Note the difference after the 6th byte. The 7th and 8th byte which is
> 00 01 shows up as 01 and 10th, 11th and 12th bytes do now show up at
> all. However I have had success getting bytes in the order such as
> below and echoing this command works fine.
> 16 06 14 34 46 11 00 00 BB 10 00 00
>
> If anyone has any idea of whats going on here then please help me.
>
> Thanx,
>
> Ray